Repository navigation
test(cuda.core): skip the VMM RDMA policy test on WSL - #3478
Conversation
GPUDirect RDMA is not supported on WSL, but some drivers report the capability there, and the RDMA-enabled VMM allocation in test_vmm_allocator_policy_configuration then fails. Skip the test on WSL; the capability checks stay as they are. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Summary
Change: Other Merge Risk:
|
|
(Unfortunately the CI for #3359 is stuck.) |
|
GPUDirect RDMA is not supported on WSL, but some drivers report the capability there, and the RDMA-enabled VMM allocation in test_vmm_allocator_policy_configuration then fails. Skip the test on WSL; the capability checks stay as they are. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 36bc530)
On WSL with an R580-family driver,
test_vmm_allocator_policy_configurationfails with cuda.core 1.3.0: the RDMA-enabled VMM allocation raisesCUDA_ERROR_UNKNOWN(tracked internally as NVBug 7103528). The test and its capability checks have not changed since 1.2.1.GPUDirect RDMA is not supported on WSL. With a newer driver on WSL, the device reports no RDMA support and the test skips; I verified this today on driver 596.71 with cuda.core 1.2.1 and 1.3.0. The cause of the failure on the older driver is not confirmed.
This PR only stops the test from running on WSL. It does not change the library or the capability checks.
🤖 Generated with Claude Code